-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closes #7 #8
base: master
Are you sure you want to change the base?
Closes #7 #8
Conversation
README.md
Outdated
@@ -23,6 +23,20 @@ git add -A | |||
git commit -m "Your commit message" | |||
git push --set-upstream origin new-branch | |||
``` | |||
The git add command lets you add a file to the staging area. You can think of the staging area as a step before the commit process in git. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you can use ' ` ' to add code snippets in a line, just like you use this '```' to add multi-line code snippets
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Replacing git add
with git add <file_name>
would be intuitive.
As long as a changeset is in the staging area, git allows you to edit it as you like. | ||
The git add -A command however, finds all new and updated files everywhere throughout the project and add them to the staging area. | ||
|
||
* Inspecting a repository |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Take a look at github markdown to format the text in .md files link
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can format your changes using markdown :) for better readability
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Format the changes using markdown
@tushar5526 Hey sure. But I'm stuck somewhere. Am I supposed to do this while being on the master branch? I'm unable to exit it and apparently there's no good solution for it on the internet. Can you help me proceed? |
@somya22 can you elaborate on your problem a little, where are you stuck ? |
@tushar5526 I am stuck on the master branch of my forked repository (Hello-World). |
Can you tell me the last command few commands you ran? You can be stuck for a lot of reasons, if there are any error messages tell me that too. |
Sure. First of all, there is an issue with syncing my fork. The Git command line showed that it is synced and my fork on Github showed that it is 10 commits behind the original. Then, 'push origin master' gave a fatal error that “origin does not appear to be a git repository”. I made changes to my forked repo and then created a pull request later. And now, Git is stuck on the master branch. |
Can you drop a Screenshot of following commands |
Need gdrive access @somya22, you can attach the files here too, just drag and drop them. |
@somya22 Do this : I think you did some mistakes syncing your fork ! |
Feel free to ask, if I was not clear enough :) |
@tushar5526 Thankyou I'll look into it. |
@tushar5526 Here's the problem. Acc to git status, changes are up to date and still, the rebase command is saying that the changes are unstaged. |
Follow this
change the last three pick to squash, then save it using
Then modify the commit messages and force push the branch back to github |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Never use your master
branch to push features. Instead you should make a branch on your fork: eg somya22/some-relevant-name
. If you make PRs from the master
branch, you won't be able to work on multiple issues simultaneously.
Closes #7 Added the necessary changes in README.md